Package Builder
Municipality package health, evidence-backed drafts, and Mincron staging concept
READ-ONLY CONCEPT

Municipality Package Health

Prioritize missing, aging, and incomplete common packages from real package, inventory, specification, and bid-history snapshots.

CurrentAging / ReviewIncompleteMissingDraft saved
MunicipalityBranchCoverageCommon package statusPackagesHistoric evidencePriority

City Workspace

Review package coverage, package health, hydrant/valve approvals, and the evidence behind suggested work.

Common Package Matrix

Click a package or generate a draft
Package family
Status
Current package
Evidence
Action

All Existing Packages

PackageFamilyItemsHealthReview flags

Draft Queue

Package Draft Builder

Start from an existing package, a similar municipality, or recurring historic package evidence. Every line remains editable and reviewable.

Choose a city and package family, then generate a draft.

Evidence Explorer

Inspect recurring bid-history package headers, product rows, and comparable city packages before approving a recommendation.

Recurring Historic Materials

MaterialExact ProductMedian QtyOccurrencesQuote SupportInventory

Comparable Package Templates

Data Sources & Safety

This concept is grounded in the same local sources already used by Input and related tools. It does not connect to or write Mincron.

What is live versus inferred

Real source data: package titles/components, inventory product status, DFW hydrant/valve approvals, and normalized historic quote package evidence. Derived concept logic: package-family classification, role completeness, aging/review flags, priority scores, comparable-city ranking, and draft confidence.
Known gap: the individual Mincron Standard Package header/detail/index files and save-side validation programs have not been mapped yet. The publish control remains locked by design.

SQL publishing discovery checklist

  1. Capture before/after rows for one disposable package created through OEC1118A.
  2. Identify header, detail, municipality index, sequence, update-user, and update-date fields.
  3. Verify whether the native save program maintains additional indexes or validation records.
  4. Implement transaction, read-back verification, rollback, and package version snapshot.
  5. Enable publish only in the test library after exact reconstruction tests pass.